Thinktanq.ai / Capacity Reservation Surface
Open Reservations Open · Non-Binding LOI Stage
Rev. 05.19.26 | Index N° TQ-SOL-CR-001
TQ · SOL · Capacity Reservation / Solano County, California / Vaca-Dixon Corridor / Adjacent to California Forever

Reserve future compute.
MW to GW.

A non-binding capacity reservation surface, open to a small set of frontier AI labs, sovereign vehicles, and hyperscale training tenants taking forward positions on Northern California capacity in the Vaca-Dixon corridor. Powered-land position near PG&E Vaca-Dixon and WAPA 500 kV infrastructure. Anonymized cohort book — no buyer names released in any external surface.

Stage 50 – 500+ MW indicative bands  ·  ≤ 12 counterparties  ·  Non-binding LOI  ·  Direct-to-principal review
Principal line +1 (510) 301-5972 · Frontier-cohort counterparties bypass the form.
Fig. 01.0
Indicative
Capacity Envelope
Indicative campus capacity envelope · cohort allocation Indicative · subject to utility process · not a commitment
Phase 1
Frontier Cohort 42%
Priority 26%
Standard 18%
Reserve 14%
Phase 2
Frontier 32%
Priority 18%
Standard 15%
Reserve / TBD 35%
MW band ▸
0 ~100 ~200 ~300 ~400 ~500+
Frontier AI Cohort
Direct-to-principal · 150–500+ MW
Priority Cohort
LOI-track · 50–150 MW
Standard Cohort
Requirement filed · 25–50 MW
Reserve
Unallocated · expansion / TBD
§ 02.0
Product
What is being reserved

A reservable path to future AI / HPC capacity in a campus-scale Vaca-Dixon position.

Narrative

This is not a tenant reservation against existing capacity. It is a structured, dated process to take ranked priority on future Northern California AI/HPC capacity emerging from a campus-scale powered-land position near PG&E Vaca-Dixon and WAPA 500 kV infrastructure.

Submitting a capacity requirement places your organization into an anonymized cohort book. Executing a non-binding Letter of Interest promotes you into the priority queue with a dated review cadence. NDA-stage materials, site detail, and allocation discussion follow on the cohort track.

Reservable attributeCurrent positioning
RegionSolano County, California · Northern California load zone
CorridorVaca-Dixon · PG&E substation + WAPA 500 kV adjacency
Campus scaleCampus-scale powered-land position · sufficient for multi-phase delivery
Capacity bands offered25 – 500+ MW per counterparty · phase-dependent & non-binding
Reservation productCapacity requirement filing · non-binding Letter of Interest · cohort ranking · direct-to-principal track for frontier scale
Counterparty fitFrontier AI labs · sovereign AI vehicles · hyperscale training tenants · neoclouds · regulated compute users
AnonymityBuyer names withheld from any external book. Archetypes only.
PostureReservations open Open · LOI stage
Reservation discipline · what this is not
No claim of secured MW. No claim of secured interconnection. No tenant lease, no service agreement, and no PPA is being offered at this stage. References to PG&E Vaca-Dixon and WAPA 500 kV infrastructure are diligence-organized adjacency, not delivered capacity rights.
§ 03.0
Thesis
Why reserve now

Ranking on future capacity is decided early.

Thesis

AI infrastructure demand has outpaced utility interconnection, entitlement, transmission planning, transformer procurement, water and cooling, and local land-use processes. The scarce commodity is no longer datacenter floor space; it is credible paths to future power.

Counterparties who organize their capacity requirements before a position is fully de-risked end up ranked earlier in the eventual allocation. Late entrants pay institutional pricing on a known book; early entrants pay the cost of a structured process.

A dated reservation today is structurally cheaper than a queue position after allocation.

Fig. 03.1 · Reservation path  /  current cohort position
Step 01 Inquiry Public-page review. Reservation framework, cohort posture.
Step 02 · Open Requirement Filed Capacity requirement form filed. Anonymized cohort placement.
Step 03 Letter of Interest Non-binding LOI signed. Priority queue + dated review.
Step 04 NDA Site detail, power-path summary, indicative capacity ranges.
Step 05 Reservation Allocation review · dedicated capacity discussion.
Step 06 Allocation Definitive documents · service / lease / PPA architecture.
Position marker reflects the current open stage in the reservation surface. Movement through stages is gated by counterparty fit, dated milestones, and posture of the upstream diligence stack.
§ 04.0
Site
Site & corridor framing

Vaca-Dixon corridor adjacency — public-page framing.

Framing

The campus is positioned in Solano County near PG&E Vaca-Dixon and WAPA 500 kV infrastructure. Public-page materials describe corridor adjacency only. Parcel-level detail, APN matrices, easements, and the formal power-path workstream are NDA-gated and released to counterparties on the cohort track.

Solano corridor & campus envelope — public-page schematic Indicative · Not to scale · Parcel detail withheld · NDA-gated
N 0 2 mi 4 mi WAPA 500 kV CORRIDOR ▸ PG&E VACA-DIXON REGIONAL CONTEXT PG&E TRANSMISSION ▸ I-80 Campus envelope CAMPUS-SCALE POWERED-LAND POSITION PARCEL DETAIL · NDA-GATED
Campus envelope
Public-page framing only
PG&E Vaca-Dixon
Regional substation context
WAPA 500 kV
Federal corridor adjacency
I-80 access
Highway corridor
§ 06.0
Cohorts
Cohort tiers · reservation framework

Three cohort tiers. One principle: ranking is earned by structure and speed, not by stated headline size.

Framing

The reservation surface organizes counterparties into three cohorts. Submission of a capacity requirement is the entry point; cohort promotion is gated by signed LOI, dated review cadence, and counterparty fit. Cohort assignment is reversible and does not represent any commitment of capacity, service, or interconnection.

Cohort 02LOI-track

Priority Cohort

Band · 50 – 150 MW · Ranked queue · LOI-required

For counterparties prepared to execute a non-binding Letter of Interest covering a defined MW band, sponsor capability, and timing posture. Promoted into the dated review cadence at the cohort track.

  • Ranked queue position
  • Dated allocation review
  • NDA-stage materials on cadence
  • Reservation discussion on the cohort track
Entry pathSigned LOI
Cohort 03Open

Standard Cohort

Band · 25 – 50 MW · Deferred allocation

Entry-stage cohort for counterparties filing a capacity requirement but not yet ready to execute an LOI. Anonymized placement; promotion is available on declared LOI execution.

  • Anonymized cohort placement
  • Deferred allocation review
  • Public-page materials only
  • Promotion path to Priority on LOI
Entry pathCapacity requirement filed
Cohort assignment is reversible and non-binding Submit Requirement
§ 07.0
Receipts
What you receive at each stage

Material release follows the reservation path.

Framing

Each stage of the reservation path releases a defined set of materials, opens a defined process step, and asks for a defined counterparty action. Nothing released at an earlier stage requires anything more than a public-page review.

01
Inquiry
Public-page review · reservation framework · cohort posture · indicative capacity envelope · framework FAQ.
Counterparty stepPublic-page only
02
Requirement Filed
Anonymized cohort placement · acknowledgement of MW band · confirmation of cohort track · dated review cadence framing.
Counterparty stepCapacity requirement form
03
Letter of Interest
Priority queue position · NDA package outline · LOI templating · reservation-stage process schedule · sponsor diligence framing.
Counterparty stepSigned non-binding LOI
04
NDA Stage
Site detail · campus map · power-path summary · indicative capacity ranges by phase · constraints framing · third-party work-product release approved for cohort track.
Counterparty stepExecuted mutual NDA
05
Reservation
Allocation review · dedicated capacity discussion · phase / MW envelope alignment · indicative service architecture · counterparty-aligned diligence path.
Counterparty stepCohort allocation review
06
Allocation
Definitive documents · service / lease / PPA architecture · interconnection workstream alignment · delivery schedule under utility process.
Counterparty stepDefinitive documentation
§ 08.0
Eligibility
Who this is for

Eligible counterparties & workload archetypes.

Framing

The reservation surface is open to AI/HPC compute users with credible workload definitions, demonstrable sponsor capability, and a willingness to operate inside a structured, dated cohort process. Eligibility is reviewed at every stage; cohort placement is reversible.

Counterparty categories
  • Frontier AI labDirect briefing
  • Sovereign AI vehicleFrontier cohort
  • Hyperscale training tenant150 – 500+ MW
  • Neocloud / GPU platformPriority cohort
  • Foundation-model platformLOI-track
  • Defense / simulation / classifiedRegulated
  • Biotech / EDA / quant computeRegulated
  • Robotics / autonomy trainingTraining-heavy
Workload archetypes
  • Frontier trainingNext-gen scale
  • Long-horizon trainingMulti-year
  • Inference at scaleLatency-tolerant
  • Hybrid training + inferenceMixed PUE
  • Classified / sovereign / regulatedJurisdictional
  • Bursty research computeReserved + scheduled
  • High-density / DLCLiquid-cooled
§ 09.0
Submit
Submit a capacity requirement

File a capacity requirement.

Framing

Filing a capacity requirement is the entry point to the reservation surface. Submission places your organization into the anonymized cohort book and starts the LOI conversation. No commitment is implied at this stage; cohort placement and movement are reviewed against eligibility, structure, and posture.

Open a direct line.

Two paths in. Frontier-cohort counterparties (150 – 500+ MW, sovereign, hyperscale training) bypass the form and request a direct briefing. Counterparties at 50 MW or below file a capacity requirement and enter the cohort book.

Anonymity preserved · No buyer names or logos released in any external cohort book · Public-page materials remain open while the request is under review.

Cohort placement on submitStandard Cohort · Pending review
Review cadence1 business day
External anonymizationBuyer archetype only
Binding postureNon-binding
Logged · Reviewed within 1 business day · TQ-SOL-CR-001
§ 10.0
FAQ
Frequently raised reservation questions

What compute users usually ask first.

Q.01Is this binding?+
No. Filing a capacity requirement is a non-binding intake into the cohort book. A non-binding Letter of Interest promotes you into the priority queue with a dated review cadence — it remains non-binding until reservation-stage documents and definitive transaction documents are executed.
Q.02When can I expect a capacity allocation?+
Allocation timing follows the upstream diligence and utility-process posture and is released on the cohort track. The reservation surface is structured so that queue position is decided early; allocation timing is decided by the gating power-path and entitlement workstreams as they advance.
Q.03What proof do you have today?+
Public-page proof is limited to land-scale framing, corridor adjacency, and the reservation framework. Source documents — utility-process artifacts, third-party work product, parcel-level detail — are NDA-gated and released to counterparties on the cohort track.
Q.04Will my name appear anywhere?+
No. Buyer names are withheld from any external cohort book. Public-facing materials and external diligence books reference counterparty archetypes only (e.g. "tier-1 neocloud", "sovereign AI vehicle", "defense / simulation user"). Identities are disclosed only to the upstream diligence counterparties under separate NDA, if at all.
Q.05How is cohort placement decided?+
Cohort placement is a function of counterparty category, workload definition, sponsor capability, MW band, timing posture, and willingness to execute a non-binding LOI. Placement is reversible at any stage and does not commit capacity, service, or interconnection.
Q.06What is the Letter of Interest?+
The LOI is a non-binding document covering MW band, sponsor capability, timing posture, and a stated intent to operate inside the cohort process. Signing the LOI promotes the counterparty into the Priority Cohort with a dated review cadence; it does not commit pricing, capacity, or interconnection.
Q.07Can I file a strategic / large requirement?+
Yes. Strategic Cohort handles requirements at 150 – 250+ MW, sovereign AI vehicles, defense / regulated compute, and bespoke jurisdictional structures. Strategic intake is direct-to-cohort-review rather than queued.
Q.08How does this relate to the developer / JV process?+
The reservation surface and the upstream developer / JV process are separate. The reservation surface captures end-user capacity requirements; the developer / JV process places control of the campus position with the counterparty best able to convert that demand into delivered capacity. Developer / JV brief →
Editorial discipline · Anti-pattern register
"Secured" MW "Available capacity" Specific allocation dates Tenant lease / PPA quotes Named other tenants Land sale language JV economics Per-MW pricing Stock data-center photography Neon AI visuals